home *** CD-ROM | disk | FTP | other *** search
- 1 - 2. _I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n This chapter lists supplemental information to the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e. The information listed here is product- and release-specific; use it with the Installation Guide to install this product. 2.1 _C_o_m_m_o_n__D_e_s_k_t_o_p__E_n_v_i_r_o_n_m_e_n_t__S_u_b_s_y_s_t_e_m_s Common Desktop Environment includes these subsystems: _c_d_e._s_w._c_l_i_e_n_t CDE Client Configuration, 5.3. Client-side files outside ////uuuussssrrrr////ddddtttt, which enable CDE startup etc. This is mandatory for every system running CDE. It is the only subsystem required on clients with an NFS-mounted ////uuuussssrrrr////ddddtttt. _c_d_e._s_w._e_o_e CDE Execution Environment, 5.3. Base software for run- time environment. _c_d_e._s_w._d_s_o CDE Shared Libraries, 5.3. Software libraries required to run any CDE programs. _c_d_e._s_w._t_e_r_m_i_n_f_o CDE Terminfo Data, 5.3. Terminal information file for ddddtttttttteeeerrrrmmmm. This could be installed on systems which will be accessed via ddddtttttttteeeerrrrmmmms even though CDE may not be installed. _c_d_e._s_w._t_e_d_s_c_a_p_e CDE TEDscape, 5.3. TEDscape enhances the Netscape Navigator to be a CDE compliant application. _c_d_e._s_w._a_p_p_b_u_i_l_d_e_r CDE Application Builder, 5.3. A development tool for developing CDE applications. _c_d_e._s_w._h_e_l_p_b_u_i_l_d_e_r CDE Online Help Builder, 5.3. Online help builder for CDE development environment. _c_d_e._s_w._h_d_r CDE Developer Header Files, 5.3. Header files for CDE - 2 - development environment. _c_d_e._s_w._l_i_b CDE Developer Static Libraries, 5.3. Static versions of software libraries from _c_d_e._s_w._d_s_o, for the CDE development environment. _c_d_e._m_a_n._r_e_l_n_o_t_e_s CDE Release Notes, 5.3. _c_d_e._m_a_n._e_o_e__b_o_o_k_s CDE EOE Books, 5.3. PDF-format books for CDE run-time environment. _c_d_e._m_a_n._e_o_e__h_e_l_p CDE EOE Online Help, 5.3. Online help pages for CDE run-time environment. _c_d_e._m_a_n._e_o_e__m_a_n CDE EOE Manual Pages, 5.3. Manual pages for CDE run-time environment. _c_d_e._m_a_n._d_e_v__b_o_o_k_s CDE Developer Books, 5.3. PDF-format books for CDE development environment. _c_d_e._m_a_n._d_e_v__m_a_n CDE Developer Manual Pages. Manual pages for CDE development environment. _c_d_e._d_e_m_o._d_e_v CDE Developer Demos, 5.3. Example source code for CDE development environment. 2.2 _C_o_m_m_o_n _D_e_s_k_t_o_p _E_n_v_i_r_o_n_m_e_n_t _S_u_b_s_y_s_t_e_m _D_i_s_k _S_p_a_c_e _R_e_q_u_i_r_e_m_e_n_t_s This section lists the subsystems (and their sizes) of Common Desktop Environment. If you are installing this product for the first time, the subsystems marked ``default'' are the ones that are installed if you use the ``go'' menu item. To install a different set of subsystems, use the ``install,'' ``remove,'' ``keep,'' and ``step'' commands in _i_n_s_t to customize the list of subsystems to be installed, then select the ``go'' menu item. Note: The listed subsystem sizes are approximate. Refer to the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for information - 3 - on finding exact sizes. If you install every subsystem, approximately 130 MB of disk space will be required. A default installation requires approximately 50 MB. Subsystem Name Subsystem Size (1 KB blocks) _c_d_e._d_e_m_o._d_e_v 857 _c_d_e._m_a_n._d_e_v__b_o_o_k_s 20,179 _c_d_e._m_a_n._d_e_v__m_a_n 3,342 _c_d_e._m_a_n._e_o_e__b_o_o_k_s 26,406 _c_d_e._m_a_n._e_o_e__h_e_l_p (default) 11,047 _c_d_e._m_a_n._e_o_e__m_a_n (default) 1,345 _c_d_e._m_a_n._r_e_l_n_o_t_e_s (default) 33 _c_d_e._s_w._a_p_p_b_u_i_l_d_e_r 10,875 _c_d_e._s_w._c_l_i_e_n_t (default) 5 _c_d_e._s_w._d_s_o (default) 9,815 _c_d_e._s_w._e_o_e (default) 23,893 _c_d_e._s_w._h_d_r 1,091 _c_d_e._s_w._h_e_l_p_b_u_i_l_d_e_r 3,101 _c_d_e._s_w._l_i_b 12,594 _c_d_e._s_w._t_e_d_s_c_a_p_e 897 _c_d_e._s_w._t_e_r_m_i_n_f_o (default) 2 2.3 _I_n_s_t_a_l_l_a_t_i_o_n__M_e_t_h_o_d All of the subsystems for Common Desktop Environment can be installed using IRIX's iiiinnnnsssstttt or sssswwwwmmmmggggrrrr. You do not need to use the miniroot. Refer to the _I_R_I_S _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e for complete installation instructions. Before installation, any previous installation of TED should be removed using the command ////uuuussssrrrr////ddddtttt////aaaaddddmmmmiiiinnnn////ddddeeeeiiiinnnnssssttttaaaallllllll. See the TED Installation Guide for details. 2.4 _P_r_e_r_e_q_u_i_s_i_t_e_s If you want to install ccccddddeeee....sssswwww....cccclllliiiieeeennnntttt, you must also install xxxx____eeeeooooeeee....sssswwww....XXXXooooppppttttffffoooonnnnttttssss, xxxx____eeeeooooeeee....sssswwww....eeeeooooeeee, ccccddddeeee....sssswwww....tttteeeerrrrmmmmiiiinnnnffffoooo and ttttoooooooollllttttaaaallllkkkk____eeeeooooeeee....sssswwww....rrrruuuunnnnttttiiiimmmmeeee. - 4 - If you want to install ccccddddeeee....sssswwww....eeeeooooeeee, you must also install ccccddddeeee....sssswwww....cccclllliiiieeeennnntttt, ccccddddeeee....sssswwww....ddddssssoooo and ttttoooooooollllttttaaaallllkkkk____eeeeooooeeee....sssswwww....rrrruuuunnnnttttiiiimmmmeeee. If you want to install ccccddddeeee....sssswwww....tttteeeeddddssssccccaaaappppeeee, you must also install ccccddddeeee....sssswwww....eeeeooooeeee and nnnneeeettttssssccccaaaappppeeee....sssswwww....cccclllliiiieeeennnntttt. If you want to install ccccddddeeee....sssswwww....hhhhddddrrrr, you must also install ccccddddeeee....sssswwww....eeeeooooeeee. If you want to install ccccddddeeee....sssswwww....lllliiiibbbb, you must also install ccccddddeeee....sssswwww....hhhhddddrrrr. If you want to install ccccddddeeee....sssswwww....hhhheeeellllppppbbbbuuuuiiiillllddddeeeerrrr, you must also install ccccddddeeee....sssswwww....eeeeooooeeee and ccccddddeeee....mmmmaaaannnn....eeeeooooeeee____hhhheeeellllpppp. If you want to install ccccddddeeee....mmmmaaaannnn....eeeeooooeeee____hhhheeeellllpppp, you must also install ccccddddeeee....sssswwww....eeeeooooeeee. If you want to install ccccddddeeee....ddddeeeemmmmoooo....ddddeeeevvvv, you must also install ccccddddeeee....sssswwww....hhhhddddrrrr. If you want to install ccccddddeeee....sssswwww....aaaappppppppbbbbuuuuiiiillllddddeeeerrrr, you must also install ccccddddeeee....sssswwww....hhhhddddrrrr, C compiler and frontend packages. The Application Manager has pre-configured application icons for a number of IRIX/Magic applications, e.g. Insight. These will not work if the appropriate application packages are not installed. 2.5 _C_o_n_f_i_g_u_r_a_t_i_o_n__F_i_l_e_s There are many configuration files in CDE. These are discussed in the Common Desktop Environment: Advanced User's and System Administrator's Guide. 2.6 _O_t_h_e_r__I_n_s_t_a_l_l_a_t_i_o_n__I_n_f_o_r_m_a_t_i_o_n 2.6.1 _I_n_s_t_a_l_l_i_n_g__w_i_t_h__N_F_S_-_m_o_u_n_t_e_d__/_u_s_r_/_d_t It is possible to install CDE so that the bulk of CDE is installed into an NFS-mounted ////uuuussssrrrr////ddddtttt//// directory. In this case the subsystem _c_d_e._s_w._c_l_i_e_n_t needs to be installed on each machine which is mounting the remaining CDE subsystems from an NFS server. After the subsystem is installed, follow section 2.7.2 to enable CDE. - 5 - 2.6.2 _E_n_a_b_l_i_n_g__C_D_E After installation, CDE needs to be enabled as root. This can be done in either of two ways: 1. Execute the command ddddttttccccoooonnnnffffiiiigggg ----eeee. 2. cccchhhhkkkkccccoooonnnnffffiiiigggg ddddttttllllooooggggiiiinnnn oooonnnn and cccchhhhkkkkccccoooonnnnffffiiiigggg xxxxddddmmmm ooooffffffff This enables CDE services, and arranges that the CDE login service ddddttttllllooooggggiiiinnnn will come up after you next reboot your machine. 2.6.3 _D_i_s_a_b_l_i_n_g__C_D_E To switch back to using xxxxddddmmmm as the login service, run either of the following as root: 1. Execute the command ////uuuussssrrrr////ddddtttt////bbbbiiiinnnn////ddddttttccccoooonnnnffffiiiigggg ----dddd. 2. cccchhhhkkkkccccoooonnnnffffiiiigggg ddddttttllllooooggggiiiinnnn ooooffffffff and cccchhhhkkkkccccoooonnnnffffiiiigggg xxxxddddmmmm oooonnnn This arranges that xxxxddddmmmm acts as the login service after the next reboot of your machine. It does NOT disable other CDE services. 2.6.4 _A_l_l_o_w_i_n_g__A_c_c_e_s_s__t_o__U_s_e_r_s__w_i_t_h_o_u_t__a__P_a_s_s_w_o_r_d By default, users without a password cannot log in. To disable this facility, remove the keyword ppppaaaasssssssswwwwdddd____rrrreeeeqqqquuuuiiiirrrreeeedddd from the following line in ////eeeettttcccc////ddddtttt////ccccoooonnnnffffiiiigggg////ppppaaaammmm....ccccoooonnnnffff: ddddttttllllooooggggiiiinnnn aaaauuuutttthhhh rrrreeeeqqqquuuuiiiirrrreeeedddd ////uuuussssrrrr////ddddtttt////lllliiiibbbb////sssseeeeccccuuuurrrriiiittttyyyy////ppppaaaammmm____uuuunnnniiiixxxx....ssssoooo....1111 ppppaaaasssssssswwwwdddd____rrrreeeeqqqquuuuiiiirrrreeeedddd 2.6.5 _S_w_i_t_c_h_i_n_g__t_o__C_D_E 2.6.5.1 _G_u_i_d_e_l_i_n_e_s__f_o_r__U_s_e_r_s__o_f__O_t_h_e_r__D_e_s_k_t_o_p_s If you have previously used the _I_n_d_i_g_o _M_a_g_i_c _D_e_s_k_t_o_p the following points will help ease your transition to using the Common Desktop Environment: +o Preferences that you previously set from the Toolchest Menu can now be set from the CDE Style manager. This includes items such as Colors, Fonts, Mouse controls and so forth. +o Many of the tools you previously accessed through the Toolchest Menu and the Icon Catalog can now be accessed - 6 - from the CDE Application Manager. 2.6.5.2 _G_e_n_e_r_a_l _G_u_i_d_e_l_i_n_e_s _f_o_r _P_r_e_v_i_o_u_s _X _W_i_n_d_o_w _S_y_s_t_e_m _U_s_e_r_s If you have previously run X11, you must be aware of the following major differences between a standard X11 environment and the SGI CDE. +o CDE does not use a startup script (such as $$$$HHHHOOOOMMMMEEEE////....xxxxiiiinnnniiiittttrrrrcccc or $$$$HHHHOOOOMMMMEEEE////....xxxx11111111ssssttttaaaarrrrtttt). The functionality of the startup script is replaced by the CDE Session Manager. +o CDE does not automatically load a user-specific resource file (e.g. $$$$HHHHOOOOMMMMEEEE////....XXXXddddeeeeffffaaaauuuullllttttssss). Resources are loaded for a CDE session by the Session Manager. +o The $$$$HHHHOOOOMMMMEEEE////....pppprrrrooooffffiiiilllleeee (or $$$$HHHHOOOOMMMMEEEE////....llllooooggggiiiinnnn) file is not explicitly used by CDE. You can request that these files be read (or sourced) in by modifying the $$$$HHHHOOOOMMMMEEEE////....ddddttttpppprrrrooooffffiiiilllleeee file. +o CDE uses the CDE Window Manager (based on the Motif Window Manager, mmmmwwwwmmmm). +o If you have previously run the X Window System, you may have an entry in your $$$$HHHHOOOOMMMMEEEE////....pppprrrrooooffffiiiilllleeee (or $$$$HHHHOOOOMMMMEEEE////....llllooooggggiiiinnnn) file that runs ....xxxx11111111ssssttttaaaarrrrtttt. You must remove this entry; otherwise, the script may run when you log into the system and request that your ....llllooooggggiiiinnnn be sourced. 2.6.6 _M_o_v_i_n_g__y_o_u_r__R_e_s_o_u_r_c_e_s__i_n_t_o__C_D_E Before you incorporate previous resources into the CDE environment, you should carefully examine them and choose only those features that you want in the new environment. Keep in mind that resources that specify fonts and colours for clients will prevent the CDE Style Manager from customizing those resources. There are two ways to incorporate resources you have already been using into the CDE environment: +o Resources to be applied system-wide (for all users) can be placed into ////uuuussssrrrr////ddddtttt////ccccoooonnnnffffiiiigggg////CCCC////ssssyyyyssss....rrrreeeessssoooouuuurrrrcccceeeessss. before any users have run a CDE session. This file is read by the Session Manager the first time a user logs into CDE. However, be aware that this file - 7 - is not read once the user has run a CDE session and has a $$$$HHHHOOOOMMMMEEEE////....ddddtttt////sssseeeessssssssiiiioooonnnnssss////ccccuuuurrrrrrrreeeennnntttt____oooorrrr____hhhhoooommmmeeee////ddddtttt....rrrreeeessssoooouuuurrrrcccceeeessss file saved by the Session Manager. +o Resources to be applied on a per-user basis are best merged into the user's resource database during a CDE session. To merge the resources: a. Copy $$$$HHHHOOOOMMMMEEEE////....XXXXddddeeeeffffaaaauuuullllttttssss to a new file. b. Edit the new file to specify the resources you wished passed into the CDE environment. c. Execute the following command from a terminal window running during a session: xxxxrrrrddddbbbb ----mmmmeeeerrrrggggeeee ----nnnnooooccccpppppppp <<<<ffffiiiilllleeeennnnaaaammmmeeee>>>> where <<<<ffffiiiilllleeeennnnaaaammmmeeee>>>> is the name of the edited file. This merges the resources into the X servers RRRREEEESSSSOOOOUUUURRRRCCCCEEEE____MMMMAAAANNNNAAAAGGGGEEEERRRR property string. 2.6.7 _E_n_v_i_r_o_n_m_e_n_t__V_a_r_i_a_b_l_e_s The login manager has various environment variables built in. It also provides ways to: +o Override the built-in values. +o Add additional environment variables. Both system-wide and personal variables can be specified. +o System-wide variables are placed in: ////eeeettttcccc////ddddtttt////ccccoooonnnnffffiiiigggg////XXXXccccoooonnnnffffiiiigggg +o The eeeennnnvvvviiiirrrroooonnnnmmmmeeeennnntttt resource is used to set the value of environment resources. For example, the following line specifies a system-wide editor and language: DDDDttttllllooooggggiiiinnnn****eeeennnnvvvviiiirrrroooonnnnmmmmeeeennnntttt:::: EEEEDDDDIIIITTTTOOOORRRR====vvvviiii LLLLAAAANNNNGGGG====CCCC +o Variables specified on a per-display basis are placed in: ////eeeettttcccc////ddddtttt////bbbbiiiinnnn////XXXXsssseeeessssssssiiiioooonnnn +o User-specific variables are set in $$$$HHHHOOOOMMMMEEEE////....ddddttttpppprrrrooooffffiiiilllleeee. The ....ddddttttpppprrrrooooffffiiiilllleeee file should contain only variable settings. It should contain neithe shell commands that require terminal I/O nor commands that run in the foreground. To execute the users ....llllooooggggiiiinnnn file at the time you log in, the appropriate source command for the user's shell type (sssshhhh,,,, - 8 - ccccsssshhhh oooorrrr kkkksssshhhh) must first be uncommented. The source commands are the last two entries in the $$$$HHHHOOOOMMMMEEEE////....ddddttttpppprrrrooooffffiiiilllleeee. 2.6.8 _S_w_i_t_c_h_i_n_g__t_o__t_h_e__d_t_w_m__W_i_n_d_o_w__M_a_n_a_g_e_r This section describes migrating settings from mmmmwwwwmmmm to ddddttttwwwwmmmm. Similar actions are required to switch from 4444DDDDwwwwmmmm to ddddttttwwwwmmmm. If you have been using the mmmmwwwwmmmm window manager, switching to the ddddttttwwwwmmmm window manager involves: +o Moving the customizations from the mmmmwwwwmmmm configuration file ($$$$HHHHOOOOMMMMEEEE////....mmmmwwwwmmmmrrrrcccc) into the ddddttttwwwwmmmmrrrrcccc configuration file ($$$$HHHHOOOOMMMMEEEE////....ddddtttt////ddddttttwwwwmmmmrrrrcccc). To do this: a. Copy ////uuuussssrrrr////ddddtttt////ccccoooonnnnffffiiiigggg////CCCC////ssssyyyyssss....ddddttttwwwwmmmmrrrrcccc to $$$$HHHHOOOOMMMMEEEE////....ddddtttt////ddddttttwwwwmmmmrrrrcccc. Give the new file write permission. b. Copy the customizations you've made in ....mmmmwwwwmmmmrrrrcccc into ddddttttwwwwmmmmrrrrcccc. c. If necessary, use the following ddddttttwwwwmmmm resources to define the custom button bindings and key bindings you want to use: ddddttttwwwwmmmm****bbbbuuuuttttttttoooonnnnBBBBiiiinnnnddddiiiinnnnggggssss:::: BBBBuuuuttttttttoooonnnnBBBBiiiinnnnddddiiiinnnnggggssssSSSSeeeettttNNNNaaaammmmeeee ddddttttwwwwmmmm****kkkkeeeeyyyyBBBBiiiinnnnddddiiiinnnnggggssss:::: KKKKeeeeyyyyBBBBiiiinnnnddddiiiinnnnggggssssSSSSeeeettttNNNNaaaammmmeeee d. If you want to use a different workspace (root) menu, replace the button binding: <<<<BBBBttttnnnn1111DDDDoooowwwwnnnn>>>> rrrrooooooootttt ffff....mmmmeeeennnnuuuu DDDDttttRRRRoooooooottttMMMMeeeennnnuuuu <<<<BBBBttttnnnn3333DDDDoooowwwwnnnn>>>> rrrrooooooootttt ffff....mmmmeeeennnnuuuu DDDDttttRRRRoooooooottttMMMMeeeennnnuuuu with <<<<BBBBttttnnnn1111DDDDoooowwwwnnnn>>>> rrrrooooooootttt ffff....mmmmeeeennnnuuuu mmmmyyyy____mmmmeeeennnnuuuu____nnnnaaaammmmeeee <<<<BBBBttttnnnn3333DDDDoooowwwwnnnn>>>> rrrrooooooootttt ffff....mmmmeeeennnnuuuu mmmmyyyy____mmmmeeeennnnuuuu____nnnnaaaammmmeeee e. Change any mmmmwwwwmmmm resources to ddddttttwwwwmmmm resources in the resource database. For example, you would need to change the resource. MMMMwwwwmmmm****kkkkeeeeyyyybbbbooooaaaarrrrddddFFFFooooccccuuuussssPPPPoooolllliiiiccccyyyy:::: ppppooooiiiinnnntttteeeerrrr to: DDDDttttwwwwmmmm****kkkkeeeeyyyybbbbooooaaaarrrrddddFFFFooooccccuuuussssPPPPoooolllliiiiccccyyyy:::: ppppooooiiiinnnntttteeeerrrr There are three ways to modify the resource database for the window manager. The way you choose depends on - 9 - the scope of the change and whether or not the user has already run a CDE session: +o To provide system-wide resources, you can edit the file ////eeeettttcccc////ddddtttt////aaaapppppppp----ddddeeeeffffaaaauuuullllttttssss////CCCC////DDDDttttwwwwmmmm Note, however, that this file could be replaced by future CDE updates. +o The file ////eeeettttcccc////ddddtttt////ccccoooonnnnffffiiiigggg////CCCC////ssssyyyyssss....rrrreeeessssoooouuuurrrrcccceeeessss is read by the Session Manager the first time a user logs into CDE. Thus, you can place system-wide resources there. However, be aware that this file is not read once the user has run a CDE session and has a resource database saved by the session manager. +o Once the user has run a CDE session, user-specific resources are added directly to the RRRREEEESSSSOOOOUUUURRRRCCCCEEEE____MMMMAAAANNNNAAAAGGGGEEEERRRR property string. See "Moving your Resources to the CDE Environment" earlier. To replace your XXXX11111111 startup script for CDE sessions: +o Log into a CDE session. +o Use a terminal emulator to start the applications that were previously started from your XXXX11111111 startup script. Do not start a window manager (the CDE window manager will already be running). +o You now have two choices: a. You can proceed with your session, opening and closing applications as necessary. your next session will start the applications running at the end of your previous session. This is the default behaviour. b. You can save and use the same session each time you log in. 
